Really glad to be here again and get the chance to speak here, so thank you very much.

What do we want to talk about?

One topic that I work on since many, many years, software architecture, and another

topic I work on since not that many years, but also some time ago, agile development.

And in my projects, there's always a clash if it comes to these two topics.

The last six and a half, seven years, I'm doing agile projects.

There we switched from the classic approach to agile approaches with our customers.

And I was in the role of the architect there, and as it is in these agile projects, they

told me the coaches and the teams, they told me, no, Guy, Vanna, we don't need you.

This is agile development, in agile development everything is different.

There is no architect in agile development.

In agile development, architecture evolves, emerges by itself from the work of the team.

And the best quote I heard some months ago in my current project from a guy we're working

on a microservice architecture who stated the quote, with microservices there is nothing

like architecture.

Okay, that's it, we can go to lunch and then it's fine, right?

Let's wait and see.

Yes, I'm here, okay, I'm here, I'm not working with my client, because my client don't need

an architect anymore, right?

No, let's look into this.

I'm here, I'm earning my money with software architecture, so there must be more than these

quotes.

So, let's have first of all a look, or recall what is architecture.

And what do you do today if you want to know a definition of something like architecture

of a topic, you Google it, right?

So I just Googled some days ago, I Googled what is architecture, and first of all I found

Wikipedia.

I don't want to go through all of these lines here.

You can read it by yourself, but I think the most important parts are there.

It says something about macroscopic, it says important, and it already says hard to change.

And this is something one guy whose name you really should remember, whose books you really

should read, Martin Fowler, this guy really knows what he's doing, stated architecture

in one sentence, he said software architecture are those decisions which are both important

and hard to change.

And this is the main definition to differ between what is design, software design, and

what is software architecture, as the line isn't that hard.

So the important parts are we are macroscopic, it's the big stuff that's architecture.

This is why the architects are the cool guys and that's why I became an architect and stuff

like that.

No, not really.

It's the important stuff, okay.

But the most important wording here is, and this is what they both had here, they both

say important and they both say hard to change.

So if you already look at the slide and think about, okay, they are important decisions,

and once you make them, they're hard to change, and then you rethink, ah, software architecture,

we don't need an HR development as from the design of the teams, it just emerges.

And the team, when you think how should I implement it, left way or the right way, don't

know, let's try the left way.

And it was an important decision, hard to change, and it was the wrong decision.

Not sure if this is the right way to make this decision, so the message here is it's